| Course Name | Software Verification and Validation |
| Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
|---|---|---|---|---|---|
| SE 318 | Spring | 2 | 2 | 3 | 7 |
| Prerequisites |
| ||||||||
| Course Language | English | ||||||||
| Course Type | Required | ||||||||
| Course Level | First Cycle | ||||||||
| Mode of Delivery | Online | ||||||||
| Teaching Methods and Techniques of the Course | Group WorkPractical demonstrationLecturing / Presentation | ||||||||
| Course Coordinator | |||||||||
| Course Lecturer(s) | |||||||||
| Assistant(s) | |||||||||
| Course Objectives | The primary objective of this course is to introduce students to, and provide core competencies in the fundamentals and principles of software testing. The secondary objective is to make the students familiar with the basic testing methods and technologies which are necessary for applying the concepts of quality assurance to obtain a high quality software product. The third objective of this course is to provide delegates with the necessary skills to implement software testing qualifications compliant with the requirements of the international software testing certifications. Both goals are addressed by recognizing software test processes, test documentation, test techniques, test management and supporting tools. |
| Learning Outcomes | The students who succeeded in this course;
|
| Course Description | It is generally accepted that it is not possible to create perfect software. It is therefore necessary to test software before it is released to the users in order to reduce the risk of mistakes in software production having a negative impact when the software is used. It is equally necessary to ensure that testing is performed well. This course specifies definitions and concepts, test processes, test documentation, test techniques in software engineering. |
| Related Sustainable Development Goals | |
|
| Core Courses | X |
| Major Area Courses | ||
| Supportive Courses | ||
| Media and Managment Skills Courses | ||
| Transferable Skill Courses |
| Week | Subjects | Required Materials |
| 1 | Fundamentals of software testing | Based on Chapter 1 of Black, van Veenendaal and Graham: Foundations of Software Testing, 3rd ed., Cengage Learning, 2012. |
| 2 | Software testing. | Based on Chapter 8 of Sommerville, Ian: Software Engineering, (10th ed.), Pearson, 2016. |
| 3 | Testing throughout the software life cycle Lab: Testing in SDLC and test documentation | Based on Chapter 2 of Black’s book. |
| 4 | Static techniques Lab: Software inspection and cyclomatic complexity | Based on Chapter 3 of Black’s book. |
| 5 | Test Design Techniques: The Test Development Process Lab: Component testing - unit testing: JUnit | Based on Chapter 4 of Black’s book |
| 6 | Test Design Techniques: Black Box testing techniques Lab: Component testing - unit testing: JUnit, module and program testing | Based on Chapter 4 of Black’s book |
| 7 | Test Design Techniques: White Box testing techniques Lab: Decision table testing and equivalence partitioning | Based on Chapter 4 of Black’s book |
| 8 | Review | |
| 9 | Test Management Lab: Software testing framework for web applications: Selenium IDE | Based on Chapter 5 of Black’s book. |
| 10 | Quality Management Lab: Load testing tool for web applications: Jmeter | Based on Chapter 24 of Sommerville’s book. |
| 11 | Quality Management Lab: Load testing tool for web applications: Jmeter | Based on Chapter 24 of Sommerville’s book. |
| 12 | Mutation testing, calculation of the cost of executed mutants | Mutation Testing Techniques, Applications and Tools |
| 13 | Case study 1 | National Transportation Communications for ITS Protocol Object Definitions for Dynamic Message Signs (DMS) |
| 14 | Case study 2 | Online shop example, Marathon example |
| 15 | Review | |
| 16 | Review of the Semester |
| Course Notes/Textbooks |
|
| Suggested Readings/Materials |
|
| Semester Activities | Number | Weigthing |
| Participation | ||
| Laboratory / Application | ||
| Field Work | ||
| Quizzes / Studio Critiques | - | - |
| Portfolio | ||
| Homework / Assignments | ||
| Presentation / Jury | ||
| Project | 1 | 20 |
| Seminar / Workshop | ||
| Oral Exam | ||
| Midterm | 1 | 30 |
| Final Exam | 1 | 50 |
| Total |
| Weighting of Semester Activities on the Final Grade | 2 | 50 |
| Weighting of End-of-Semester Activities on the Final Grade | 1 | 50 |
| Total |
| Semester Activities | Number | Duration (Hours) | Workload |
|---|---|---|---|
| Course Hours (Including exam week: 16 x total hours) | 16 | 2 | 32 |
| Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | 2 | |
| Study Hours Out of Class | 14 | 4 | 56 |
| Field Work | |||
| Quizzes / Studio Critiques | - | - | |
| Portfolio | |||
| Homework / Assignments | |||
| Presentation / Jury | |||
| Project | 1 | 30 | |
| Seminar / Workshop | |||
| Oral Exam | |||
| Midterms | 1 | 20 | |
| Final Exams | 1 | 30 | |
| Total | 200 |
| # | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
| 1 | To have adequate knowledge in Mathematics, Science, Computer Science and Software Engineering; to be able to use theoretical and applied information in these areas on complex engineering problems. | X | ||||
| 2 | To be able to identify, define, formulate, and solve complex Software Engineering problems; to be able to select and apply proper analysis and modeling methods for this purpose. | X | ||||
| 3 | To be able to design, implement, verify, validate, document, measure and maintain a complex software system, process, or product under realistic constraints and conditions, in such a way as to meet the requirements; ability to apply modern methods for this purpose. | X | ||||
| 4 | To be able to devise, select, and use modern techniques and tools needed for analysis and solution of complex problems in software engineering applications; to be able to use information technologies effectively. | X | ||||
| 5 | To be able to design and conduct experiments, gather data, analyze and interpret results for investigating complex Software Engineering problems. | |||||
| 6 | To be able to work effectively in Software Engineering disciplinary and multi-disciplinary teams; to be able to work individually. | X | ||||
| 7 | To be able to communicate effectively in Turkish, both orally and in writing; to be able to author and comprehend written reports, to be able to prepare design and implementation reports, to be able to present effectively, to be able to give and receive clear and comprehensible instructions. | |||||
| 8 | To have knowledge about global and social impact of engineering practices and software applications on health, environment, and safety; to have knowledge about contemporary issues as they pertain to engineering; to be aware of the legal ramifications of Engineering and Software Engineering solutions. | |||||
| 9 | To be aware of ethical behavior, professional and ethical responsibility; to have knowledge about standards utilized in engineering applications. | |||||
| 10 | To have knowledge about industrial practices such as project management, risk management, and change management; to have awareness of entrepreneurship and innovation; to have knowledge about sustainable development. | |||||
| 11 | To be able to collect data in the area of Software Engineering, and to be able to communicate with colleagues in a foreign language. ("European Language Portfolio Global Scale", Level B1) | |||||
| 12 | To be able to speak a second foreign language at a medium level of fluency efficiently. | |||||
| 13 | To recognize the need for lifelong learning; to be able to access information, to be able to stay current with developments in science and technology; to be able to relate the knowledge accumulated throughout the human history to Software Engineering. | |||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest
